Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1182

reference
916-tree-1
name
1182
tree-preservation-order

undefined

916-tpo-1
uprn
address-text
point
POINT (-1.029836 50.867235)
geometry
MULTIPOLYGON (((-1.029751 50.867226,-1.029755 50.867242,-1.029767 50.867257,-1.029785 50.867270,-1.029809 50.867277,-1.029835 50.867280,-1.029862 50.867278,-1.029886 50.867270,-1.029905 50.867259,-1.029917 50.867244,-1.029922 50.867227,-1.029918 50.867210,-1.029906 50.867195,-1.029888 50.867183,-1.029864 50.867175,-1.029838 50.867172,-1.029811 50.867175,-1.029787 50.867182,-1.029768 50.867194,-1.029756 50.867209,-1.029751 50.867226)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL